archive: first use rename, if failed, use file.copy()+file.remove(), …#374
Merged
gaow merged 1 commit intoStatFunGen:mainfrom Apr 10, 2025
Merged
archive: first use rename, if failed, use file.copy()+file.remove(), …#374gaow merged 1 commit intoStatFunGen:mainfrom
gaow merged 1 commit intoStatFunGen:mainfrom
Conversation
Contributor
|
I see! okay that makes sense. Then indeed you have to copy and delete. That seems the only way to work it with S3 bucket. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
archive: first use rename, if failed, use file.copy()+file.remove(), also message warnings.
In cloud environments, the source directory and target directory are often located on different file systems or partitions. When attempting to move files across different file systems using the
file.rename()function, the operating system returns an "Invalid cross-device link" error. This occurs because the rename system call can only operate within the same file system, as it's designed to simply update directory entries rather than physically move data between storage devices.